This chapter describes Thin Server NFS Client (TSNC) messages. For information on message content and how to use the message, refer to the Introduction.
| TSNC.001 |
Level: U-INFO
Short Syntax: TSNC.001 Starting NFS Client full Refresh
Long Syntax: TSNC.001 Starting NFS Client full Refresh
Description: NFS Client has started full refresh
| TSNC.002 |
Level: U-INFO
Short Syntax: TSNC.002 Completing NFS Client full Refresh
Long Syntax: TSNC.002 Completing NFS Client full Refresh
Description: NFS Client has completed full refresh
| TSNC.003 |
Level: U-INFO
Short Syntax: TSNC.003 Refresh for Directory host_file_name will be processed ( reason)
Long Syntax: TSNC.003 Refresh for Directory host_file_name will be processed ( reason)
Description: This message is generated during a refresh to indicate that a sub-directory will be processed and why.
| TSNC.004 |
Level: U-INFO
Short Syntax: TSNC.004 Refresh for Directory host_file_name will be skipped ( reason)
Long Syntax: TSNC.004 Refresh for Directory host_file_name will be skipped ( reason)
Description: This message is generated during a refresh to indicate that a sub-directory will be skipped and why.
| TSNC.005 |
Level: UI-ERROR
Short Syntax: TSNC.005 Invalid file of type st_mode ( host_file_name), mode :
Long Syntax: TSNC.005 Invalid file of type st_mode ( host_file_name), mode :
Description: This message is generated when a file is found during a refresh or individual file update which is not a regular file, symbolic link, or a directory.
| TSNC.006 |
Level: UI-ERROR
Short Syntax: TSNC.006 No memory to process host_file_name
Long Syntax: TSNC.006 No memory to process host_file_name
Description: This message is generated when the Thin Server Feature is unable to process a file or directory because it ran out of memory.
Cause: The master file server is an NT server with NSM code prior to the August 1998 fix level.
Action: Update the NSM code.
| TSNC.007 |
Level: U-INFO
Short Syntax: TSNC.007 Refresh for File host_file_name will be processed
Long Syntax: TSNC.007 Refresh for File host_file_name will be processed
Description: This message is generated during a refresh to indicate that a file will be processed.
| TSNC.008 |
Level: U-INFO
Short Syntax: TSNC.008 Refresh for File host_file_name is complete
Long Syntax: TSNC.008 Refresh for File host_file_name is complete
Description: This message is generated when the update for a file is complete.
| TSNC.009 |
Level: U-INFO
Short Syntax: TSNC.009 Refresh for File host_file_name will be skipped ( reason)
Long Syntax: TSNC.009 Refresh for File host_file_name will be skipped ( reason)
Description: This message is generated during a refresh to indicate that a file will be skipped.
| TSNC.010 |
Level: UI-ERROR
Short Syntax: TSNC.010 OpenFile call for file_name returned error_description( error_code)
Long Syntax: TSNC.010 OpenFile call for file_name returned error_description( error_code)
Description: NFS Client couldn't open a cached copy of host_file_name on hard file.
Cause: TSDK_NO_CANT_WRITE
Action: Too many files are being cached. Make sure sufficient memory is available on the router or adjust the configuration to reduce the number of cached files.
Cause: Any other code
Action: An internal code error has occured.
| TSNC.011 |
Level: UI-ERROR
Short Syntax: TSNC.011 nfs_proc call for host_file_name returned error_description( error_code)
Long Syntax: TSNC.011 nfs_proc call for host_file_name returned error_description( error_code)
Description: A problem has occured in accessing a file on the master file server.
Cause: NFSERR_PERM, NFSERR_ACCES, MNT_EPERM, MNT_EACCESS
Action: The file being accessed may have permissions set such that the Thin Server does not have permission to access the file. Correct the permissions on the file if the file is intended to be accessible to the Thin Server.
Cause: NFSERR_NOENT, MNT_ENOENT, NFSERR_EXIST
Action: The file doesn't exist on the Master File Server. This may indicate a failure in operation of the NFS or Mount daemons on the Master File Server. Use the REFRESH command in Talk 5 or SNMP to force a new refresh, if the error continues to occur, verify operation of the Master File Server
Cause: NFSERR_IO, NFSERR_NXIO
Action: I/O Errors occured on the Master File Server. Verify correct operation of the Master File Server.
Cause: NFSERR_NOTDIR, NFSERR_ISDIR, NFSERR_STALE
Action: Files were changed on the Master File Server while a refresh or single file update was in progress. Use the REFRESH command in Talk 5 or SNMP to force a new refresh after the file updates on the Master File Server are complete.
Cause: NFS client operation not available
Action: The Master File Server is not functioning correctly, check that the NFS and Mount daemons are running and properly configured.
Cause: NFS client operation timed out
Action: The NFS Client retries have been exhausted due to time outs. Make sure the connection to the Master File Server is operational, and that the Master File Server itself is operational.
Cause: others
Action: Verify correct operation of the Master File Server.
| TSNC.012 |
Level: UI-ERROR
Short Syntax: TSNC.012 Update File for host_file_name returned error_description( error_code)
Long Syntax: TSNC.012 Update File for host_file_name returned error_description( error_code)
Description: The NFS client was unable to update a cached file.
Action: The cached files are using too much space. If a hard file is not used, increase the amount of memory used by the cache. If this is not possible, or a hard file is being used, modify the configuration to reduce the number of files cached. A flush from Talk 5 may also be helpfull to eliminate files which are no longer used.
Cause: Any other error
Action: An internal code error has occured.
| TSNC.013 |
Level: UI-ERROR
Short Syntax: TSNC.013 file_operation of host_file_name at Offset file_offset returned error_description( error_code)
Long Syntax: TSNC.013 file_operation of host_file_name at Offset file_offset returned error_description( error_code)
Description: A problem has occured in accessing a file on the master file server. See the causes and actions for TSNC_11.
| TSNC.014 |
Level: UI-ERROR
Short Syntax: TSNC.014 WriteFileRequest call for host_file_name returned error_description( error_code)
Long Syntax: TSNC.014 WriteFileRequest call for host_file_name returned error_description( error_code)
Description: This message is generated when a write to the Thin Server cache fails.
Cause: TSDK_CACHE_WRITE_ERROR
Action: The thin server is not using a hard file and ran out of memory in the cache for the specified file.
Cause: TSDK_SCHED_CANCELED
Action: A restart or other action caused the file update to be interrupted. No action is necessary, the next refresh will recover the file.
Cause: TSDK_DISK_IO_ERROR
Action: A disk IO error occured while writing the file to the hard file. Make sure the hard file is not corrupted.
Cause: Any other error
Action: An internal code error has occured.
| TSNC.015 |
Level: UI-ERROR
Short Syntax: TSNC.015 LookUpNode call for host_file_name returned error_description( error_code)
Long Syntax: TSNC.015 LookUpNode call for host_file_name returned error_description( error_code)
Description: The NFS client was unable to resolve a file name in the thin server cache. This is an internal code error.
| TSNC.016 |
Level: UI-ERROR
Short Syntax: TSNC.016 Resolve for host_file_name returned error_description( error_code)
Long Syntax: TSNC.016 Resolve for host_file_name returned error_description( error_code)
Description: This message is generated when the NFS client is attempting to resolve a file name on the master file server.
Cause: NFSERR_NOENT
Action: The file was being requested from a "Yes, inlcude sub-directories" directory and does not exist on the Master File Server. If the file is supposed to exist on the Master File Server, make sure that the Thin Server has permission to access the file.
Cause: NFSERR_PERM, NFSERR_ACCES, MNT_EPERM, MNT_EACCESS
Action: The file being accessed may have permissions set such that the Thin Server does not have permission to access the file. Correct the permissions on the file if the file is intended to be accessible to the Thin Server.
Cause: MNT_ENOENT, NFSERR_EXIST
Action: The file doesn't exist on the Master File Server. This may indicate a failure in operation of the NFS or Mount daemons on the Master File Server. Use the REFRESH command in Talk 5 or SNMP to force a new refresh, if the error continues to occur, verify operation of the Master File Server
Cause: NFSERR_IO, NFSERR_NXIO
Action: I/O Errors occured on the Master File Server. Verify correct operation of the Master File Server.
Cause: NFSERR_NOTDIR, NFSERR_ISDIR, NFSERR_STALE
Action: Files were changed on the Master File Server while a refresh or single file update was in progress. Use the REFRESH command in Talk 5 or SNMP to force a new refresh after the file updates on the Master File Server are complete.
Cause: NFS client operation not available
Action: The Master File Server is not functioning correctly, check that the NFS and Mount daemons are running and properly configured.
Cause: NFS client operation timed out
Action: The NFS Client retries have been exhausted due to time outs. Make sure the connection to the Master File Server is operational, and that the Master File Server itself is operational.
Cause: TSDK_NO_TOO_MANY_NODES
Action: Too many files are being cached or too many directories exist within the directories configured for caching all files in all sub-directories. Modify the configuration to reduce the number of files or directories cached. A flush from Talk 5 may also be helpfull to eliminate files which are no longer used.
Cause: Any other error
Action: An internal code error has occured.
| TSNC.017 |
Level: UI-ERROR
Short Syntax: TSNC.017 WriteFileRequest call for host_file_name returned errno error_description( error_code)
Long Syntax: TSNC.017 WriteFileRequest call for host_file_name returned errno error_description( error_code)
Description: A disk IO error occured while writing a file into the cache. The hard file may be corrupted.
| TSNC.018 |
Level: UI-ERROR
Short Syntax: TSNC.018 AddDirectory for host_file_name returned error_description( error_code)
Long Syntax: TSNC.018 AddDirectory for host_file_name returned error_description( error_code)
Description: This message is generated when the NFS client is unable to create a directory on the thin server corresponding to a directory on the master file server.
| TSNC.019 |
Level: C-TRACE
Short Syntax: TSNC.019 TRC: trace_message
Long Syntax: TSNC.019 TRACE: trace_message
Description: This message is generated when NFS Client internal traces are used.
| TSNC.020 |
Level: C-INFO
Short Syntax: TSNC.020 Create Incl Dir include_directory, sub-dirs: local_directory
Long Syntax: TSNC.020 Create Include Directory include_directory, include sub-directories: local_directory
Description: This message is generated when the configuration is processed.
| TSNC.021 |
Level: U-INFO
Description: The Primary(Secondary) Master Server is being used.
| TSNC.022 |
Level: UI-ERROR
Short Syntax: TSNC.022 INT ERR: function for object returned error_description( error_code)
Long Syntax: TSNC.022 INTERNAL ERROR: function for object returned error_description( error_code)
Description: This message is generated when NFS Client internal errors occur.
| TSNC.023 |
Level: UE-ERROR
Short Syntax: TSNC.023 action ( host_file_name) failed, too many nodes: num_files files, num_links sym lnks, num_dirs dirs, num_other other, TOT: num_total nodes
Long Syntax: TSNC.023 action ( host_file_name) failed, too many nodes: num_files files, num_links symbolic links, num_dirs directories, num_other other, TOTAL: num_total nodes
Description: The Thin Server Feature NFS directory node structure has filled and there is no more room for additional files or directories. Alter the configuration to reduce the number of directories from which files are cached and/or flush the cached files to remove learned files which are no longer needed.
Cause: Large number of "other" files
Action: Whenever a file is requested which does not exist on the host, a node entry is created for it to improve response time to the NFS client. A large number of these suggest that the clients may be configured improperly. Flush the cache to remove these entries.
| TSNC.024 |
Level: C-INFO
Short Syntax: TSNC.024 Update check host_file_name
Long Syntax: TSNC.024 Update check host_file_name
Description: This message is generated when a network station accesses a file. The NFS client will verify that the file is up to date. If the file is in a directory which is part of a tree of directories specified by a configured include directory which includes all sub-directories, the file will be added to the cache if necessary.
| TSNC.025 |
Level: CE-ERROR
Short Syntax: TSNC.025 RESERVED x
Long Syntax: TSNC.025 RESERVED x
Description: RESERVED
| TSNC.026 |
Level: UE-ERROR
Short Syntax: TSNC.026 RESERVED x
Long Syntax: TSNC.026 RESERVED x
Description: RESERVED
| TSNC.027 |
Level: UE-ERROR
Short Syntax: TSNC.027 RPC Error in function is error_description( error_code), additional_description( additional_code, additional_code)
Long Syntax: TSNC.027 RPC Error in function is error_description( error_code), additional_description( additional_code, additional_code)
Description: This message is generated when an RPC call fails.
Cause: Can't decode result, Incompatible versions of RPC, Server can't decode arguments, Port mapper failure, Program not registered
Action: The Master File Server has returned an invalid response. Make sure the Master File Server is running the correct server software.
Cause: Unable to send, Unable to receive, Unknown host, Unknown protocol
Action: There may be a problem with communication to the Master File Server. Make sure the IP interface being used is operational.
Cause: Timed out
Action: The operation has timed out. A few timeouts are expected. If too many timeouts are occuring, check the connection to the Master File Server.
Cause: Authentication error
Action: Some Master File Servers must be able to resolve a name for the Thin Server. If the Thin Server does not have an entry in a Domain Name Server for the IP address on the interface used to connect to the Master File Server, an entry might be added to the Master File Server's "hosts" file.
Cause: Program unavailable, Program/version mismatch, Procedure unavailable
Action: The Port Mapper, NFS, or Mount daemons are not running on the Master File Server. Make sure they are running and properly configured.
Cause: Remote system error
Action: Some kind of error has occurred on the Master File Server. Make sure the Master File Server is operating correctly.
Cause: Others
Action: An internal error has occurred.
| TSNC.028 |
Level: UE-ERROR
Short Syntax: TSNC.028 Include directory directory could not be resolved because reason
Long Syntax: TSNC.028 Include directory directory could not be resolved because reason
Description: This message is generated when one of the configured include directories is unable to be resolved to a valid mount exported by the master file server.
Cause: No nfs directories exported
Action: Make sure the master file server is exporting the required directories, and that the thin server has access to them
Cause: No export matched
Action: Make sure that the include directories are properly configured and that the correct master file server is configured. Also note that file names are cause sensitive.
| TSNC.029 |
Level: UI-ERROR
Short Syntax: TSNC.029 NFS Client initialization failed because function returned error_description( error_code)
Long Syntax: TSNC.029 NFS Client initialization failed because function returned error_description( error_code)
Description: This error is recorded if the Thin Server NFS Client fails to initialize because of an internal error.
| TSNC.030 |
Level: UE-ERROR
Short Syntax: TSNC.030 Failed to connect to Master File Server daemon daemon, error error_description
Long Syntax: TSNC.030 Failed to connect to Master File Server daemon daemon, error error_description
Description: This error is reported when the NFS fails to connect to either the <ount or NFS daemons on the Master File Server.
| TSNC.031 |
Level: UE-ERROR
Short Syntax: TSNC.031 No exported directories on master server
Long Syntax: TSNC.031 No exported directories on master server
Description: This error is reported when the master server has no exported directories.
| TSNC.032 |
Level: U-INFO
Short Syntax: TSNC.032 function failed, retrying count of maximum times
Long Syntax: TSNC.032 function failed, retrying count of maximum times
Description: This error is reported to indicate that the NFS Client is retrying an operation.